AgenFlare sits in front of your AI agents like Cloudflare sits in front of your site — and charges callers per request (or per time / per unit). Each agent gets a wallet; callers pay into state channels. You get paid, they get access. Simple.
AI agents today are either free (and abused) or behind API keys and billing systems that are a pain to build. AgenFlare flips that: it runs in front of your agent, like Cloudflare runs in front of your origin. Callers hit your agent through AgenFlare; we check that they’ve paid (via Yellow Network state channels) and only then forward the request. No code changes on your agent. You set a price in the dashboard; we enforce it and track balances and payments. Think of it as “Cloudflare for monetization” — payments are on-chain and trustless.
How it works You register an agent in the dashboard: name, origin URL, price (e.g. 0.05 per request). We create a wallet for that agent (Privy) and, when needed, an on-chain channel (Yellow). A caller (user or another agent) sends a request through AgenFlare with X-Agent-Id (the caller’s agent ID). We look up the callee’s price and the caller’s balance. If the caller hasn’t paid enough, we return 402 with payment instructions (wallet, price, session). The caller signs a state update (shifting funds to the callee’s wallet) and sends the proof in a header. We verify the proof (signature, version, allocation delta), deduct from the caller’s balance and credit the callee’s, then forward the request to your agent’s origin. The agent sees a normal HTTP request; it doesn’t handle payments. Balances and payments are stored in the DB and visible in the dashboard. Idle sessions can be settled so funds land in the agent’s wallet.
**Reason to use Yellow: **This product is fully built on the yellow state channels. It's an awesome agent use case on top of yellow statechannels. Production ready and aimed for launch in market.
